js-ipfs deprecation - replaced by Helia #585
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a blog post accompanying the js-ipfs deprecation work that is active at ipfs/js-ipfs#4336
Why now?
We were originally going to do a discuss.ipfs.tech post (proposed text). Doing this as a blog entry will cause the discuss.ipfs.tech post to be generated while getting broader reach for the message.
Switching from a discuss.ipfs.tech post to a blog entry came to mind when thinking about the next IPFS Newsletter. I know we can manually submit newsletter additions, but this should get it scooped up by default.
(With deprecations, the more expansive the communication the better to avoid surprises.)
Shouldn't we add more text about Helia?
Ideally yes, but I'm just taking the discuss.ipfs.tech text we had drafted. We will followup with an "announcing Helia" post where we can give more info about Helia.
Do we need to act quickly?
If folks aren't comfortable with this blog entry and more work is required, we can park it and should just fall back to a discuss.ipfs.tech post.
Open items